Repository navigation
ci: keep release tooling when checking out the release PR - #482
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The release job fails before it can update the release PR's lockfiles (run). It installs dependencies on
mainand then checks out the release PR branch, but that checkout cleans the workspace and deletesnode_modules.bun install --lockfile-onlydoesn't install anything, sosync:lockfilecan't loadtypescriptand the job stops.The release PR checkout now uses
clean: false, so the dependencies installed frommainstay available for the lockfile scripts. The checkout still replaces every tracked file with the release branch.🤖 Generated with Claude Code